Meshtastic App/com.geeksville.mesh/[androidJvm]MeshProtos/ToRadio/Builder

Builder

class Builder : GeneratedMessage.Builder<BuilderT> , MeshProtos.ToRadioOrBuilder


Packets/commands to the radio will be written (reliably) to the toRadio characteristic.
Once the write completes the phone can assume it is handled.

Protobuf type meshtastic.ToRadio

Functions

build

open fun build(): MeshProtos.ToRadio

buildPartial

open fun buildPartial(): MeshProtos.ToRadio

clear

open fun clear(): MeshProtos.ToRadio.Builder

clearDisconnect

open fun clearDisconnect(): MeshProtos.ToRadio.Builder


Tell API server we are disconnecting now.
This is useful for serial links where there is no hardware/protocol based notification that the client has dropped the link.
(Sending this message is optional for clients)

bool disconnect = 4;

clearHeartbeat

open fun clearHeartbeat(): MeshProtos.ToRadio.Builder


Heartbeat message (used to keep the device connection awake on serial)

.meshtastic.Heartbeat heartbeat = 7;

clearMqttClientProxyMessage

open fun clearMqttClientProxyMessage(): MeshProtos.ToRadio.Builder


MQTT Client Proxy Message (for client / phone subscribed to MQTT sending to device)

.meshtastic.MqttClientProxyMessage mqttClientProxyMessage = 6;

clearPacket

open fun clearPacket(): MeshProtos.ToRadio.Builder


Send this packet on the mesh

.meshtastic.MeshPacket packet = 1;

clearPayloadVariant

open fun clearPayloadVariant(): MeshProtos.ToRadio.Builder

clearWantConfigId

open fun clearWantConfigId(): MeshProtos.ToRadio.Builder


Phone wants radio to send full node db to the phone, This is
typically the first packet sent to the radio when the phone gets a
bluetooth connection. The radio will respond by sending back a
MyNodeInfo, a owner, a radio config and a series of
FromRadio.node_infos, and config_complete
the integer you write into this field will be reported back in the
config_complete_id response this allows clients to never be confused by
a stale old partially sent config.

uint32 want_config_id = 3;

clearXmodemPacket

open fun clearXmodemPacket(): MeshProtos.ToRadio.Builder

.meshtastic.XModem xmodemPacket = 5;

getDefaultInstanceForType

open fun getDefaultInstanceForType(): MeshProtos.ToRadio

getDescriptor

fun getDescriptor(): Descriptors.Descriptor

getDescriptorForType

open fun getDescriptorForType(): Descriptors.Descriptor

getDisconnect

open fun getDisconnect(): Boolean


Tell API server we are disconnecting now.
This is useful for serial links where there is no hardware/protocol based notification that the client has dropped the link.
(Sending this message is optional for clients)

bool disconnect = 4;

getHeartbeat

open fun getHeartbeat(): MeshProtos.Heartbeat


Heartbeat message (used to keep the device connection awake on serial)

.meshtastic.Heartbeat heartbeat = 7;

getHeartbeatBuilder

open fun getHeartbeatBuilder(): MeshProtos.Heartbeat.Builder


Heartbeat message (used to keep the device connection awake on serial)

.meshtastic.Heartbeat heartbeat = 7;

getHeartbeatOrBuilder

open fun getHeartbeatOrBuilder(): MeshProtos.HeartbeatOrBuilder


Heartbeat message (used to keep the device connection awake on serial)

.meshtastic.Heartbeat heartbeat = 7;

getMqttClientProxyMessage

open fun getMqttClientProxyMessage(): MeshProtos.MqttClientProxyMessage


MQTT Client Proxy Message (for client / phone subscribed to MQTT sending to device)

.meshtastic.MqttClientProxyMessage mqttClientProxyMessage = 6;

getMqttClientProxyMessageBuilder

open fun getMqttClientProxyMessageBuilder(): MeshProtos.MqttClientProxyMessage.Builder


MQTT Client Proxy Message (for client / phone subscribed to MQTT sending to device)

.meshtastic.MqttClientProxyMessage mqttClientProxyMessage = 6;

getMqttClientProxyMessageOrBuilder

open fun getMqttClientProxyMessageOrBuilder(): MeshProtos.MqttClientProxyMessageOrBuilder


MQTT Client Proxy Message (for client / phone subscribed to MQTT sending to device)

.meshtastic.MqttClientProxyMessage mqttClientProxyMessage = 6;

getPacket

open fun getPacket(): MeshProtos.MeshPacket


Send this packet on the mesh

.meshtastic.MeshPacket packet = 1;

getPacketBuilder

open fun getPacketBuilder(): MeshProtos.MeshPacket.Builder


Send this packet on the mesh

.meshtastic.MeshPacket packet = 1;

getPacketOrBuilder

open fun getPacketOrBuilder(): MeshProtos.MeshPacketOrBuilder


Send this packet on the mesh

.meshtastic.MeshPacket packet = 1;

getPayloadVariantCase

open fun getPayloadVariantCase(): MeshProtos.ToRadio.PayloadVariantCase

getWantConfigId

open fun getWantConfigId(): Int


Phone wants radio to send full node db to the phone, This is
typically the first packet sent to the radio when the phone gets a
bluetooth connection. The radio will respond by sending back a
MyNodeInfo, a owner, a radio config and a series of
FromRadio.node_infos, and config_complete
the integer you write into this field will be reported back in the
config_complete_id response this allows clients to never be confused by
a stale old partially sent config.

uint32 want_config_id = 3;

getXmodemPacket

open fun getXmodemPacket(): XmodemProtos.XModem

.meshtastic.XModem xmodemPacket = 5;

getXmodemPacketBuilder

open fun getXmodemPacketBuilder(): XmodemProtos.XModem.Builder

.meshtastic.XModem xmodemPacket = 5;

getXmodemPacketOrBuilder

open fun getXmodemPacketOrBuilder(): XmodemProtos.XModemOrBuilder

.meshtastic.XModem xmodemPacket = 5;

hasDisconnect

open fun hasDisconnect(): Boolean


Tell API server we are disconnecting now.
This is useful for serial links where there is no hardware/protocol based notification that the client has dropped the link.
(Sending this message is optional for clients)

bool disconnect = 4;

hasHeartbeat

open fun hasHeartbeat(): Boolean


Heartbeat message (used to keep the device connection awake on serial)

.meshtastic.Heartbeat heartbeat = 7;

hasMqttClientProxyMessage

open fun hasMqttClientProxyMessage(): Boolean


MQTT Client Proxy Message (for client / phone subscribed to MQTT sending to device)

.meshtastic.MqttClientProxyMessage mqttClientProxyMessage = 6;

hasPacket

open fun hasPacket(): Boolean


Send this packet on the mesh

.meshtastic.MeshPacket packet = 1;

hasWantConfigId

open fun hasWantConfigId(): Boolean


Phone wants radio to send full node db to the phone, This is
typically the first packet sent to the radio when the phone gets a
bluetooth connection. The radio will respond by sending back a
MyNodeInfo, a owner, a radio config and a series of
FromRadio.node_infos, and config_complete
the integer you write into this field will be reported back in the
config_complete_id response this allows clients to never be confused by
a stale old partially sent config.

uint32 want_config_id = 3;

hasXmodemPacket

open fun hasXmodemPacket(): Boolean

.meshtastic.XModem xmodemPacket = 5;

isInitialized

fun isInitialized(): Boolean

mergeFrom

open fun mergeFrom(other: MeshProtos.ToRadio): MeshProtos.ToRadio.Builder

open fun mergeFrom(other: Message): MeshProtos.ToRadio.Builder

open fun mergeFrom(input: CodedInputStream, extensionRegistry: ExtensionRegistryLite): MeshProtos.ToRadio.Builder

mergeHeartbeat

open fun mergeHeartbeat(value: MeshProtos.Heartbeat): MeshProtos.ToRadio.Builder


Heartbeat message (used to keep the device connection awake on serial)

.meshtastic.Heartbeat heartbeat = 7;

mergeMqttClientProxyMessage

open fun mergeMqttClientProxyMessage(value: MeshProtos.MqttClientProxyMessage): MeshProtos.ToRadio.Builder


MQTT Client Proxy Message (for client / phone subscribed to MQTT sending to device)

.meshtastic.MqttClientProxyMessage mqttClientProxyMessage = 6;

mergePacket

open fun mergePacket(value: MeshProtos.MeshPacket): MeshProtos.ToRadio.Builder


Send this packet on the mesh

.meshtastic.MeshPacket packet = 1;

mergeXmodemPacket

open fun mergeXmodemPacket(value: XmodemProtos.XModem): MeshProtos.ToRadio.Builder

.meshtastic.XModem xmodemPacket = 5;

setDisconnect

open fun setDisconnect(value: Boolean): MeshProtos.ToRadio.Builder


Tell API server we are disconnecting now.
This is useful for serial links where there is no hardware/protocol based notification that the client has dropped the link.
(Sending this message is optional for clients)

bool disconnect = 4;

setHeartbeat

open fun setHeartbeat(value: MeshProtos.Heartbeat): MeshProtos.ToRadio.Builder

open fun setHeartbeat(builderForValue: MeshProtos.Heartbeat.Builder): MeshProtos.ToRadio.Builder


Heartbeat message (used to keep the device connection awake on serial)

.meshtastic.Heartbeat heartbeat = 7;

setMqttClientProxyMessage

open fun setMqttClientProxyMessage(value: MeshProtos.MqttClientProxyMessage): MeshProtos.ToRadio.Builder

open fun setMqttClientProxyMessage(builderForValue: MeshProtos.MqttClientProxyMessage.Builder): MeshProtos.ToRadio.Builder


MQTT Client Proxy Message (for client / phone subscribed to MQTT sending to device)

.meshtastic.MqttClientProxyMessage mqttClientProxyMessage = 6;

setPacket

open fun setPacket(value: MeshProtos.MeshPacket): MeshProtos.ToRadio.Builder

open fun setPacket(builderForValue: MeshProtos.MeshPacket.Builder): MeshProtos.ToRadio.Builder


Send this packet on the mesh

.meshtastic.MeshPacket packet = 1;

setWantConfigId

open fun setWantConfigId(value: Int): MeshProtos.ToRadio.Builder


Phone wants radio to send full node db to the phone, This is
typically the first packet sent to the radio when the phone gets a
bluetooth connection. The radio will respond by sending back a
MyNodeInfo, a owner, a radio config and a series of
FromRadio.node_infos, and config_complete
the integer you write into this field will be reported back in the
config_complete_id response this allows clients to never be confused by
a stale old partially sent config.

uint32 want_config_id = 3;

setXmodemPacket

open fun setXmodemPacket(value: XmodemProtos.XModem): MeshProtos.ToRadio.Builder

open fun setXmodemPacket(builderForValue: XmodemProtos.XModem.Builder): MeshProtos.ToRadio.Builder

.meshtastic.XModem xmodemPacket = 5;